home *** CD-ROM | disk | FTP | other *** search
/ Columbia Kermit / kermit.zip / newsgroups / misc.19981211-19990422 / 000010_news@newsmaster….columbia.edu _Tue Dec 15 08:31:05 1998.msg < prev    next >
Internet Message Format  |  2020-01-01  |  2KB
  1. Return-Path: <news@newsmaster.cc.columbia.edu>
  2. Received: from newsmaster.cc.columbia.edu (newsmaster.cc.columbia.edu [128.59.35.30])
  3.     by watsun.cc.columbia.edu (8.8.5/8.8.5) with ESMTP id IAA22561
  4.     for <kermit.misc@watsun.cc.columbia.edu>; Tue, 15 Dec 1998 08:30:56 -0500 (EST)
  5. Received: (from news@localhost)
  6.     by newsmaster.cc.columbia.edu (8.8.5/8.8.5) id IAA00904
  7.     for kermit.misc@watsun; Tue, 15 Dec 1998 08:30:55 -0500 (EST)
  8. Path: news.columbia.edu!panix!howland.erols.net!newsfeed.nacamar.de!news.fh-hannover.de!news-han1.dfn.de!newsserver.rrzn.uni-hannover.de!not-for-mail
  9. From: "Felix E. Klee" <felix.klee@inka.de>
  10. Newsgroups: comp.protocols.kermit.misc
  11. Subject: Re: emacs config
  12. Date: Tue, 15 Dec 1998 13:00:29 +0000
  13. Organization: RRZN - Newsserver
  14. Lines: 17
  15. Message-ID: <36765D6D.848B0373@inka.de>
  16. References: <36742E71.FAD3F77@inka.de> <753kb8$8fp$1@apakabar.cc.columbia.edu>
  17. NNTP-Posting-Host: h10.stud.uni-hannover.de
  18. Mime-Version: 1.0
  19. Content-Type: text/plain; charset=us-ascii
  20. Content-Transfer-Encoding: 7bit
  21. X-Mailer: Mozilla 4.06 [en] (X11; I; Linux 2.0.34 i586)
  22. Xref: news.columbia.edu comp.protocols.kermit.misc:9642
  23.  
  24. Thanks for your respone.
  25.  
  26. John Chandler wrote:
  27. > The "[home]" in that example is a keyboard event, rather than a
  28. > character code, and it probably doesn't have an equivalent sequence of
  29. > keystrokes (in any case, I haven't found one).  This fact more-or-less
  30. > rules out the first approach.  For the second, the details depend on
  31. > exactly what codes those keys send.  For example, suppose the home key
  32. > is sending "\033[H".  You can then include the following:
  33.  
  34. How do I find out what code certain keys send?
  35.  
  36. Felix
  37.  
  38. -- 
  39. mailto:felix.klee@inka.de
  40. http://sites.inka.de/sites/klee